Instead of relying on xm create to always run the bootloader, make sure
authorkaf24@firebug.cl.cam.ac.uk <kaf24@firebug.cl.cam.ac.uk>
Fri, 28 Apr 2006 13:11:57 +0000 (14:11 +0100)
committerkaf24@firebug.cl.cam.ac.uk <kaf24@firebug.cl.cam.ac.uk>
Fri, 28 Apr 2006 13:11:57 +0000 (14:11 +0100)
commitc57010da2d0667184027c8b5dda5474c2311f0a7
tree762cd412dba309dbc96736ef53f3ac7b75c8c8a0
parent7c059c05f5233ef74cf4ed6a93188f8c507fc1ec
Instead of relying on xm create to always run the bootloader, make sure
we run it if we get into domain creation with a bootloader set but no
image.  This could happen if someone creates a domain config via the
XML-RPC or sxp interfaces.

Signed-off-by: Jeremy Katz <katzj@redhat.com>
tools/python/xen/xend/XendDomainInfo.py